chore(deps): bump lua-pure to v0.1.2, raise Go to 1.25#7
Merged
Conversation
- lua-pure v0.1.2 pins go 1.25.11, so consumers must be >= 1.25; go.mod go directive moves 1.24.6 -> 1.25.11 to satisfy it - sync user-facing requirement docs (README badge/summary en+ko, CONTRIBUTING) to Go 1.25+ and lua-pure v0.1.2 - record the bump under CHANGELOG [Unreleased] (en+ko); v0.0.1 and the benchmark measurement note stay as historical records #deps #luapure #gotoolchain Co-Authored-By: htjulia <htjulia1@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
lua-purereleased v0.1.2, which raises its own toolchain togo 1.25.11(was1.24). Because a dependency'sgodirective is a floor for consumers,go-lua-perfmust move to Go 1.25 to keep using lua-pure.Change
go.mod:lua-pure v0.1.1 → v0.1.2;go 1.24.6 → 1.25.11(auto-raised bygo getto satisfy the dependency).[Unreleased]entry (en + ko).Left as historical records (unchanged): the released
[0.0.1]changelog entry and thedocs/BENCHMARKS.md"measured on Go 1.24" note.Verification (local, go1.25.11)
go build ./...,go vet ./...,go test ./...— all passgofmt -l .clean ·govulncheck ./...exit 0Note
The
GOTOOLCHAIN=autoworkaround added for the govulncheck job is now technically redundant (the pinned toolchain is already ≥ 1.25), but it is harmless and left in place.